Activity: 07.08 - Agree Mechanics For In-Scope Projects
The purpose of this activity is to agree with the Client, incumbent (if appropriate) and other relevant service providers, on actions to be taken if the number of WIP and Planned Projects varies from the contract, at Service Handover. In addition , the gating activities for these projects and the responsibilities must also be agreed.
DescriptionWork Breakdown StructureRolesWork Product Usage
Workflow

Activity detail diagram: 07.08 - Agree Mechanics For In-Scope Projects Engagement Manager (Transition) Agree Mechanics For Variance To Agreed Plan For In-Scope Projects Agree Responsibilities And Gates For In-Scope Projects Confirm Take-On Acceptance Criteria For In-Scope Project Engagement Manager (Transition) WIP Lead Agree Mechanics For Variance To Agreed Plan For In-Scope Projects Agree Responsibilities And Gates For In-Scope Projects Confirm Take-On Acceptance Criteria For In-Scope Project WIP Lead Mechanics For In-Scope Projects Change Control Note Client Agreement Memo Agree Mechanics For Variance To Agreed Plan For In-Scope Projects Responsibility Matrix For In-Scope Projects Quality Gate Process for WIP Projects Agree Responsibilities And Gates For In-Scope Projects Acceptance Criteria For In-Scope Projects Confirm Take-On Acceptance Criteria For In-Scope Project Mechanics For In-Scope Projects Change Control Note Client Agreement Memo Agree Mechanics For Variance To Agreed Plan For In-Scope Projects Responsibility Matrix For In-Scope Projects Quality Gate Process for WIP Projects Agree Responsibilities And Gates For In-Scope Projects Acceptance Criteria For In-Scope Projects Confirm Take-On Acceptance Criteria For In-Scope Project
Work Breakdown

Copyright © 2017 Capgemini. All Rights Reserved.